| Getting Started with PCC > Configuration Options > Legacy Configuration > Configuring Ports for the Prizm Platform Services |
The Prizm Platform Services consist of several processes that are listening on various ports of the server. Most of these ports are only accessed internally from within the server by the Prizm Platform Services themselves. We recommend leaving the default ports unchanged unless they present a conflict with ports already in use on your servers.
There are three parameters in the central configuration file that determine the ports used by the Prizm Platform Services. These properties are network.publicPort, network.clustering.clusterPort, and network.internalStartingPort. A range of at least 200 ports should be left open beginning with network.internalStartingPort for internal use by the Prizm Platform Services.
If your application is hosted on a different server than the server hosting the Prizm Platform Services, then network.publicPort and network.clustering.clusterPort will need to be open in any firewalls. network.clusterPort is only used in Multi-Server Mode.
| Example |
Copy Code
|
|---|---|
network.publicPort: 18681 network.internalStartingPort: 19000 network.clustering.clusterPort: 18682 |
|
As its name implies, the Watchdog is a process that watches over all of the internal processes which make up the Prizm Platform Services. It is also responsible for starting and stopping these processes. Most of the ports used by these processes are defined in the Watchdog’s configuration file. The defaults paths for this file are:
In this file a number of ports are defined (only one or two at most need to be exposed publicly; the rest are only for internal communication on the server itself). As mentioned above, it is recommended you only change these ports if they cause port conflicts on the server hosting the Prizm Platform Services.
If your application is hosted on a different server than the server hosting the Prizm Platform Services, there is at least one port defined in the Watchdog configuration file that you will need to open in any firewalls. These ports are defined in the properties cep_port and sep_port. The cep_port is only used in Multi-Server Mode.
| Example |
Copy Code
|
|---|---|
{
…
"sep_port": 18681,
"cep_port": 18682,
…
}
|
|
Raster Conversion Service, PDF Conversion Service and AutoRedactionService Ports can no longer be updated in those respective Configuration files. When using Central Configuration, ports are allocated dynamically. If you choose to bypass the Central Configuration, these values would be set in the watchdog.config: